dmesg - AMD Ryzen 9 3950X 16-Core
pci 0000:02:0a.0: bridge window [mem 0xf7400000-0xf74fffff]
pci 0000:0a:00.0: [10de:1e81] type 00 class 0x030000
pci 0000:0a:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff]
pci 0000:0a:00.0: reg 0x14: [mem 0xe0000000-0xefffffff 64bit pref]
pci 0000:0a:00.0: reg 0x1c: [mem 0xf0000000-0xf1ffffff 64bit pref]
pci 0000:0a:00.0: reg 0x24: [io 0xf000-0xf07f]
pci 0000:0a:00.0: reg 0x30: [mem 0xf7000000-0xf707ffff pref]
pci 0000:0a:00.0: BAR 3: assigned to efifb
pci 0000:0a:00.0: PME# supported from D0 D3hot D3cold
pci 0000:0a:00.0: 32.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s x16 link at 0000:00:03.1 (capable of 126.016 Gb/s with 8 GT/s x16 link)
pci 0000:0a:00.1: [10de:10f8] type 00 class 0x040300
pci 0000:0a:00.1: reg 0x10: [mem 0xf7080000-0xf7083fff]
pci 0000:0a:00.2: [10de:1ad8] type 00 class 0x0c0330
pci 0000:0a:00.2: reg 0x10: [mem 0xf2000000-0xf203ffff 64bit pref]
pci 0000:0a:00.2: reg 0x1c: [mem 0xf2040000-0xf204ffff 64bit pref]
pci 0000:0a:00.2: PME# supported from D0 D3hot D3cold
pci 0000:0a:00.3: [10de:1ad9] type 00 class 0x0c8000
pci 0000:0a:00.3: reg 0x10: [mem 0xf7084000-0xf7084fff]
pci 0000:0a:00.3: PME# supported from D0 D3hot D3cold
pci 0000:00:03.1: PCI bridge to [bus 0a]
pci 0000:00:03.1: bridge window [io 0xf000-0xffff]
pci 0000:00:03.1: bridge window [mem 0xf6000000-0xf70fffff]
pci 0000:00:03.1: bridge window [mem 0xe0000000-0xf20fffff 64bit pref]
pci 0000:0b:00.0: [1022:148a] type 00 class 0x130000
pci 0000:0b:00.0: enabling Extended Tags
pci 0000:00:07.1: PCI bridge to [bus 0b]
pci 0000:0c:00.0: [1022:1485] type 00 class 0x130000
pci 0000:0c:00.0: enabling Extended Tags
pci 0000:0c:00.1: [1022:1486] type 00 class 0x108000
pci 0000:0c:00.1: reg 0x18: [mem 0xf7b00000-0xf7bfffff]
pci 0000:0c:00.1: reg 0x24: [mem 0xf7c08000-0xf7c09fff]
pci 0000:0c:00.1: enabling Extended Tags
pci 0000:0c:00.3: [1022:149c] type 00 class 0x0c0330
pci 0000:0c:00.3: reg 0x10: [mem 0xf7a00000-0xf7afffff 64bit]
pci 0000:0c:00.3: enabling Extended Tags
pci 0000:0c:00.3: PME# supported from D0 D3hot D3cold
pci 0000:0c:00.4: [1022:1487] type 00 class 0x040300
pci 0000:0c:00.4: reg 0x10: [mem 0xf7c00000-0xf7c07fff]
pci 0000:0c:00.4: enabling Extended Tags
pci 0000:0c:00.4: PME# supported from D0 D3hot D3cold
pci 0000:00:08.1: PCI bridge to [bus 0c]
pci 0000:00:08.1: bridge window [mem 0xf7a00000-0xf7cfffff]
pci 0000:0d:00.0: [1022:7901] type 00 class 0x010601
pci 0000:0d:00.0: reg 0x24: [mem 0xf7e00000-0xf7e007ff]
pci 0000:0d:00.0: enabling Extended Tags
pci 0000:0d:00.0: PME# supported from D3hot D3cold
pci 0000:00:08.2: PCI bridge to [bus 0d]
pci 0000:00:08.2: bridge window [mem 0xf7e00000-0xf7efffff]
pci 0000:0e:00.0: [1022:7901] type 00 class 0x010601
pci 0000:0e:00.0: reg 0x24: [mem 0xf7d00000-0xf7d007ff]
pci 0000:0e:00.0: enabling Extended Tags
pci 0000:0e:00.0: PME# supported from D3hot D3cold
pci 0000:00:08.3: PCI bridge to [bus 0e]
pci 0000:00:08.3: bridge window [mem 0xf7d00000-0xf7dfffff]
ACPI: PCI Interrupt Link [LNKA] (IRQs 4 5 7 10 11 14 15) *0
ACPI: PCI Interrupt Link [LNKB] (IRQs 4 5 7 10 11 14 15) *0
ACPI: PCI Interrupt Link [LNKC] (IRQs 4 5 7 10 11 14 15) *0
ACPI: PCI Interrupt Link [LNKD] (IRQs 4 5 7 10 11 14 15) *0
ACPI: PCI Interrupt Link [LNKE] (IRQs 4 5 7 10 11 14 15) *0
ACPI: PCI Interrupt Link [LNKF] (IRQs 4 5 7 10 11 14 15) *0
ACPI: PCI Interrupt Link [LNKG] (IRQs 4 5 7 10 11 14 15) *0
ACPI: PCI Interrupt Link [LNKH] (IRQs 4 5 7 10 11 14 15) *0
ACPI: EC: interrupt unblocked
ACPI: EC: event unblocked
ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
ACPI: EC: GPE=0x2
ACPI: \_SB_.PCI0.SBRG.EC0_: Boot DSDT EC used to handle transactions and events
iommu: Default domain type: Translated
pci 0000:0a:00.0: vgaarb: setting as boot VGA device
pci 0000:0a:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
pci 0000:0a:00.0: vgaarb: bridge control possible
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
ACPI: bus type USB registered
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti
PTP clock support registered
EDAC MC: Ver: 3.0.0
Registered efivars operations
PCI: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
Expanded resource Reserved due to conflict with PCI Bus 0000:00
e820: reserve RAM buffer [mem 0x09d02000-0x0bffffff]
e820: reserve RAM buffer [mem 0x0a200000-0x0bffffff]
e820: reserve RAM buffer [mem 0x975d7018-0x97ffffff]
e820: reserve RAM buffer [mem 0x975f7018-0x97ffffff]
e820: reserve RAM buffer [mem 0x97609018-0x97ffffff]
e820: reserve RAM buffer [mem 0xd4bca000-0xd7ffffff]
e820: reserve RAM buffer [mem 0xd752d000-0xd7ffffff]
e820: reserve RAM buffer [mem 0xd8d78000-0xdbffffff]
e820: reserve RAM buffer [mem 0xdd000000-0xdfffffff]
e820: reserve RAM buffer [mem 0x41f300000-0x41fffffff]
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
NetLabel: unlabeled traffic allowed by default
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
hpet0: 3 comparators, 32-bit 14.318180 MHz counter
clocksource: Switched to clocksource tsc-early
*** VALIDATE bpf ***
VFS: Disk quotas dquot_6.6.0
VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
*** VALIDATE ramfs ***
*** VALIDATE hugetlbfs ***
AppArmor: AppArmor Filesystem Enabled
pnp: PnP ACPI init
system 00:00: [mem 0xf8000000-0xfbffffff] has been reserved
system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
system 00:01: [mem 0xfd000000-0xfd0fffff] has been reserved
system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
system 00:03: [io 0x0290-0x029f] has been reserved
system 00:03: [io 0x0200-0x021f] has been reserved
system 00:03: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:04: [io 0x04d0-0x04d1] has been reserved
system 00:04: [io 0x040b] has been reserved
system 00:04: [io 0x04d6] has been reserved
system 00:04: [io 0x0c00-0x0c01] has been reserved
system 00:04: [io 0x0c14] has been reserved
system 00:04: [io 0x0c50-0x0c51] has been reserved
system 00:04: [io 0x0c52] has been reserved
system 00:04: [io 0x0c6c] has been reserved
system 00:04: [io 0x0c6f] has been reserved
system 00:04: [io 0x0cd0-0x0cd1] has been reserved
system 00:04: [io 0x0cd2-0x0cd3] has been reserved
system 00:04: [io 0x0cd4-0x0cd5] has been reserved
system 00:04: [io 0x0cd6-0x0cd7] has been reserved
system 00:04: [io 0x0cd8-0x0cdf] has been reserved
system 00:04: [io 0x0800-0x089f] has been reserved
system 00:04: [io 0x0b00-0x0b0f] has been reserved
system 00:04: [io 0x0b20-0x0b3f] has been reserved
system 00:04: [io 0x0900-0x090f] has been reserved
system 00:04: [io 0x0910-0x091f] has been reserved
system 00:04: [mem 0xfec00000-0xfec00fff] could not be reserved
system 00:04: [mem 0xfec01000-0xfec01fff] could not be reserved
system 00:04: [mem 0xfedc0000-0xfedc0fff] has been reserved
system 00:04: [mem 0xfee00000-0xfee00fff] has been reserved
system 00:04: [mem 0xfed80000-0xfed8ffff] could not be reserved
system 00:04: [mem 0xfec10000-0xfec10fff] has been reserved
system 00:04: [mem 0xff000000-0xffffffff] has been reserved
system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
pnp: PnP ACPI: found 5 devices
clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
pci_bus 0000:00: max bus depth: 3 pci_try_num: 4
pci 0000:02:01.0: PCI bridge to [bus 03]
pci 0000:02:01.0: bridge window [mem 0xf7900000-0xf79fffff]
pci 0000:04:00.0: BAR 9: assigned [mem 0xf7830000-0xf789ffff 64bit]
pci 0000:04:00.0: BAR 11: assigned [mem 0xf78a0000-0xf78bbfff 64bit]
pci 0000:02:03.0: PCI bridge to [bus 04]
pci 0000:02:03.0: bridge window [io 0xe000-0xefff]
pci 0000:02:03.0: bridge window [mem 0xf7800000-0xf78fffff]
pci 0000:02:05.0: PCI bridge to [bus 05]
pci 0000:02:05.0: bridge window [io 0xd000-0xdfff]
pci 0000:02:05.0: bridge window [mem 0xf7700000-0xf77fffff]
pci 0000:02:06.0: PCI bridge to [bus 06]
pci 0000:02:06.0: bridge window [mem 0xf7600000-0xf76fffff]
pci 0000:02:08.0: PCI bridge to [bus 07]
pci 0000:02:08.0: bridge window [mem 0xf7200000-0xf73fffff]
pci 0000:02:09.0: PCI bridge to [bus 08]
pci 0000:02:09.0: bridge window [mem 0xf7500000-0xf75fffff]
pci 0000:02:0a.0: PCI bridge to [bus 09]
pci 0000:02:0a.0: bridge window [mem 0xf7400000-0xf74fffff]
pci 0000:01:00.0: PCI bridge to [bus 02-09]
pci 0000:01:00.0: bridge window [io 0xd000-0xefff]
pci 0000:01:00.0: bridge window [mem 0xf7200000-0xf79fffff]
pci 0000:00:01.2: PCI bridge to [bus 01-09]
pci 0000:00:01.2: bridge window [io 0xd000-0xefff]
pci 0000:00:01.2: bridge window [mem 0xf7200000-0xf79fffff]
pci 0000:00:03.1: PCI bridge to [bus 0a]
pci 0000:00:03.1: bridge window [io 0xf000-0xffff]
pci 0000:00:03.1: bridge window [mem 0xf6000000-0xf70fffff]
pci 0000:00:03.1: bridge window [mem 0xe0000000-0xf20fffff 64bit pref]
pci 0000:00:07.1: PCI bridge to [bus 0b]
pci 0000:00:08.1: PCI bridge to [bus 0c]
pci 0000:00:08.1: bridge window [mem 0xf7a00000-0xf7cfffff]
pci 0000:00:08.2: PCI bridge to [bus 0d]
pci 0000:00:08.2: bridge window [mem 0xf7e00000-0xf7efffff]
pci 0000:00:08.3: PCI bridge to [bus 0e]
pci 0000:00:08.3: bridge window [mem 0xf7d00000-0xf7dfffff]
pci_bus 0000:00: resource 4 [io 0x0000-0x03af window]
pci_bus 0000:00: resource 5 [io 0x03e0-0x0cf7 window]
pci_bus 0000:00: resource 6 [io 0x03b0-0x03df window]
pci_bus 0000:00: resource 7 [io 0x0d00-0xffff window]
pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff window]
pci_bus 0000:00: resource 9 [mem 0x000c0000-0x000dffff window]
pci_bus 0000:00: resource 10 [mem 0xe0000000-0xfec02fff window]
pci_bus 0000:00: resource 11 [mem 0xfee00000-0xffffffff window]
pci_bus 0000:01: resource 0 [io 0xd000-0xefff]
pci_bus 0000:01: resource 1 [mem 0xf7200000-0xf79fffff]
pci_bus 0000:02: resource 0 [io 0xd000-0xefff]
pci_bus 0000:02: resource 1 [mem 0xf7200000-0xf79fffff]
pci_bus 0000:03: resource 1 [mem 0xf7900000-0xf79fffff]
pci_bus 0000:04: resource 0 [io 0xe000-0xefff]
pci_bus 0000:04: resource 1 [mem 0xf7800000-0xf78fffff]
pci_bus 0000:05: resource 0 [io 0xd000-0xdfff]
pci_bus 0000:05: resource 1 [mem 0xf7700000-0xf77fffff]
pci_bus 0000:06: resource 1 [mem 0xf7600000-0xf76fffff]
pci_bus 0000:07: resource 1 [mem 0xf7200000-0xf73fffff]
pci_bus 0000:08: resource 1 [mem 0xf7500000-0xf75fffff]
pci_bus 0000:09: resource 1 [mem 0xf7400000-0xf74fffff]
pci_bus 0000:0a: resource 0 [io 0xf000-0xffff]
pci_bus 0000:0a: resource 1 [mem 0xf6000000-0xf70fffff]
pci_bus 0000:0a: resource 2 [mem 0xe0000000-0xf20fffff 64bit pref]
pci_bus 0000:0c: resource 1 [mem 0xf7a00000-0xf7cfffff]
pci_bus 0000:0d: resource 1 [mem 0xf7e00000-0xf7efffff]
pci_bus 0000:0e: resource 1 [mem 0xf7d00000-0xf7dfffff]
NET: Registered protocol family 2
tcp_listen_portaddr_hash hash table entries: 8192 (order: 5, 131072 bytes, linear)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes, linear)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear)
TCP: Hash tables configured (established 131072 bind 65536)
UDP hash table entries: 8192 (order: 6, 262144 bytes, linear)
UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes, linear)
NET: Registered protocol family 1
NET: Registered protocol family 44
pci 0000:0a:00.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
pci 0000:0a:00.1: D0 power state depends on 0000:0a:00.0
pci 0000:0a:00.2: D0 power state depends on 0000:0a:00.0
pci 0000:0a:00.3: D0 power state depends on 0000:0a:00.0
PCI: CLS 64 bytes, default 64
Trying to unpack rootfs image as initramfs...
Initramfs unpacking failed: Decoding failed
fbcon: Taking over console
Freeing initrd memory: 81604K
pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported
pci 0000:00:01.0: Adding to iommu group 0
pci 0000:00:01.2: Adding to iommu group 1
pci 0000:00:02.0: Adding to iommu group 2
pci 0000:00:03.0: Adding to iommu group 3
pci 0000:00:03.1: Adding to iommu group 4
pci 0000:00:04.0: Adding to iommu group 5
pci 0000:00:05.0: Adding to iommu group 6
pci 0000:00:07.0: Adding to iommu group 7
pci 0000:00:07.1: Adding to iommu group 8
pci 0000:00:08.0: Adding to iommu group 9
pci 0000:00:08.1: Adding to iommu group 10
pci 0000:00:08.2: Adding to iommu group 11
pci 0000:00:08.3: Adding to iommu group 12
pci 0000:00:14.0: Adding to iommu group 13
pci 0000:00:14.3: Adding to iommu group 13
pci 0000:00:18.0: Adding to iommu group 14
pci 0000:00:18.1: Adding to iommu group 14
pci 0000:00:18.2: Adding to iommu group 14
pci 0000:00:18.3: Adding to iommu group 14
pci 0000:00:18.4: Adding to iommu group 14
pci 0000:00:18.5: Adding to iommu group 14
pci 0000:00:18.6: Adding to iommu group 14
pci 0000:00:18.7: Adding to iommu group 14
pci 0000:01:00.0: Adding to iommu group 15
pci 0000:02:01.0: Adding to iommu group 16
pci 0000:02:03.0: Adding to iommu group 17
pci 0000:02:05.0: Adding to iommu group 18
pci 0000:02:06.0: Adding to iommu group 19
pci 0000:02:08.0: Adding to iommu group 20
pci 0000:02:09.0: Adding to iommu group 21
pci 0000:02:0a.0: Adding to iommu group 22
pci 0000:03:00.0: Adding to iommu group 23
pci 0000:04:00.0: Adding to iommu group 24
pci 0000:05:00.0: Adding to iommu group 25
pci 0000:06:00.0: Adding to iommu group 26
pci 0000:07:00.0: Adding to iommu group 20
pci 0000:07:00.1: Adding to iommu group 20
pci 0000:07:00.3: Adding to iommu group 20
pci 0000:08:00.0: Adding to iommu group 21
pci 0000:09:00.0: Adding to iommu group 22
pci 0000:0a:00.0: Adding to iommu group 27
pci 0000:0a:00.1: Adding to iommu group 27
pci 0000:0a:00.2: Adding to iommu group 27
pci 0000:0a:00.3: Adding to iommu group 27
pci 0000:0b:00.0: Adding to iommu group 28
pci 0000:0c:00.0: Adding to iommu group 29
pci 0000:0c:00.1: Adding to iommu group 30
pci 0000:0c:00.3: Adding to iommu group 31
pci 0000:0c:00.4: Adding to iommu group 32
pci 0000:0d:00.0: Adding to iommu group 33
pci 0000:0e:00.0: Adding to iommu group 34
pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40
pci 0000:00:00.2: AMD-Vi: Extended features (0x58f77ef22294ade):
PPR X2APIC NX GT IA GA PC GA_vAPIC
AMD-Vi: Interrupt remapping enabled
AMD-Vi: Virtual APIC enabled
AMD-Vi: X2APIC enabled
AMD-Vi: Lazy IO/TLB flushing enabled
amd_uncore: AMD NB counters detected
amd_uncore: AMD LLC counters detected
LVT offset 0 assigned for vector 0x400
perf: AMD IBS detected (0x000003ff)
perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank).
check: Scanning for low memory corruption every 60 seconds
Initialise system trusted keyrings
Key type blacklist registered
workingset: timestamp_bits=36 max_order=22 bucket_order=0
zbud: loaded
squashfs: version 4.0 (2009/01/31) Phillip Lougher
fuse: init (API version 7.31)
*** VALIDATE fuseblk ***
*** VALIDATE fuse ***
Platform Keyring initialized
Key type asymmetric registered
Asymmetric key parser 'x509' registered
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
io scheduler mq-deadline registered
pcieport 0000:00:07.1: AER: enabled with IRQ 30
pcieport 0000:00:08.1: AER: enabled with IRQ 31
pcieport 0000:00:08.2: AER: enabled with IRQ 32
pcieport 0000:00:08.3: AER: enabled with IRQ 33
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
efifb: probing for efifb
efifb: showing boot graphics
efifb: framebuffer at 0xf1000000, using 3072k, total 3072k
efifb: mode is 1024x768x32, linelength=4096, pages=1
efifb: scrolling: redraw
efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Console: switching to colour frame buffer device 128x48
fb0: EFI VGA frame buffer device
input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
ACPI: Power Button [PWRB]
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
ACPI: Power Button [PWRF]
Monitor-Mwait will be used to enter C-1 state
ACPI: \_PR_.C000: Found 2 idle states
ACPI: \_PR_.C002: Found 2 idle states
ACPI: \_PR_.C004: Found 2 idle states
ACPI: \_PR_.C006: Found 2 idle states
ACPI: \_PR_.C008: Found 2 idle states
ACPI: \_PR_.C00A: Found 2 idle states
ACPI: \_PR_.C00C: Found 2 idle states
ACPI: \_PR_.C00E: Found 2 idle states
ACPI: \_PR_.C010: Found 2 idle states
ACPI: \_PR_.C012: Found 2 idle states
ACPI: \_PR_.C014: Found 2 idle states
ACPI: \_PR_.C016: Found 2 idle states
ACPI: \_PR_.C018: Found 2 idle states
ACPI: \_PR_.C01A: Found 2 idle states
ACPI: \_PR_.C01C: Found 2 idle states
ACPI: \_PR_.C01E: Found 2 idle states
ACPI: \_PR_.C001: Found 2 idle states
ACPI: \_PR_.C003: Found 2 idle states
ACPI: \_PR_.C005: Found 2 idle states
ACPI: \_PR_.C007: Found 2 idle states
ACPI: \_PR_.C009: Found 2 idle states
ACPI: \_PR_.C00B: Found 2 idle states
ACPI: \_PR_.C00D: Found 2 idle states
ACPI: \_PR_.C00F: Found 2 idle states
ACPI: \_PR_.C011: Found 2 idle states
ACPI: \_PR_.C013: Found 2 idle states
ACPI: \_PR_.C015: Found 2 idle states
ACPI: \_PR_.C017: Found 2 idle states
ACPI: \_PR_.C019: Found 2 idle states
ACPI: \_PR_.C01B: Found 2 idle states
ACPI: \_PR_.C01D: Found 2 idle states
ACPI: \_PR_.C01F: Found 2 idle states
serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Linux agpgart interface v0.103
loop: module loaded
libphy: Fixed MDIO Bus: probed
tun: Universal TUN/TAP device driver, 1.6
PPP generic driver version 2.4.2
VFIO - User Level meta-driver version: 0.3
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ehci-platform: EHCI generic platform driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
ohci-platform: OHCI generic platform driver
uhci_hcd: USB Universal Host Controller Interface driver
xhci_hcd 0000:07:00.1: xHCI Host Controller
xhci_hcd 0000:07:00.1: new USB bus registered, assigned bus number 1
xhci_hcd 0000:07:00.1: hcc params 0x0278ffe5 hci version 0x110 quirks 0x0000000000000410
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.06
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: xHCI Host Controller
usb usb1: Manufacturer: Linux 5.6.11-050611-generic xhci-hcd
usb usb1: SerialNumber: 0000:07:00.1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x000000007) is beyond end of object (length 0x6) (20200110/exoparg2-393)
No Local Variables are initialized for Method [_PLD]
No Arguments are initialized for method [_PLD]
ACPI Error: Aborting method \_SB.PCI0.BXBR.BYUP.BYD8.XHC1.RHUB.PRT6._PLD due to previous error (AE_AML_PACKAGE_LIMIT) (20200110/psparse-529)
xhci_hcd 0000:07:00.1: xHCI Host Controller
xhci_hcd 0000:07:00.1: new USB bus registered, assigned bus number 2
xhci_hcd 0000:07:00.1: Host supports USB 3.1 Enhanced SuperSpeed
usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.06
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: xHCI Host Controller
usb usb2: Manufacturer: Linux 5.6.11-050611-generic xhci-hcd
usb usb2: SerialNumber: 0000:07:00.1
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 4 ports detected
xhci_hcd 0000:07:00.3: xHCI Host Controller
xhci_hcd 0000:07:00.3: new USB bus registered, assigned bus number 3
xhci_hcd 0000:07:00.3: hcc params 0x0278ffe5 hci version 0x110 quirks 0x0000000000000410
usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.06
usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: xHCI Host Controller
usb usb3: Manufacturer: Linux 5.6.11-050611-generic xhci-hcd
usb usb3: SerialNumber: 0000:07:00.3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 6 ports detected
xhci_hcd 0000:07:00.3: xHCI Host Controller
xhci_hcd 0000:07:00.3: new USB bus registered, assigned bus number 4
xhci_hcd 0000:07:00.3: Host supports USB 3.1 Enhanced SuperSpeed
usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.06
usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: xHCI Host Controller
usb usb4: Manufacturer: Linux 5.6.11-050611-generic xhci-hcd
usb usb4: SerialNumber: 0000:07:00.3
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 4 ports detected
xhci_hcd 0000:0a:00.2: xHCI Host Controller
xhci_hcd 0000:0a:00.2: new USB bus registered, assigned bus number 5
xhci_hcd 0000:0a:00.2: hcc params 0x0180ff05 hci version 0x110 quirks 0x0000000000000010
usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.06
usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb5: Product: xHCI Host Controller
usb usb5: Manufacturer: Linux 5.6.11-050611-generic xhci-hcd
usb usb5: SerialNumber: 0000:0a:00.2
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
xhci_hcd 0000:0a:00.2: xHCI Host Controller
xhci_hcd 0000:0a:00.2: new USB bus registered, assigned bus number 6
xhci_hcd 0000:0a:00.2: Host supports USB 3.1 Enhanced SuperSpeed
usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.06
usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb6: Product: xHCI Host Controller
usb usb6: Manufacturer: Linux 5.6.11-050611-generic xhci-hcd
usb usb6: SerialNumber: 0000:0a:00.2
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 4 ports detected
xhci_hcd 0000:0c:00.3: xHCI Host Controller
xhci_hcd 0000:0c:00.3: new USB bus registered, assigned bus number 7
xhci_hcd 0000:0c:00.3: hcc params 0x0278ffe5 hci version 0x110 quirks 0x0000000000000410
usb usb7: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.06
usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb7: Product: xHCI Host Controller
usb usb7: Manufacturer: Linux 5.6.11-050611-generic xhci-hcd
usb usb7: SerialNumber: 0000:0c:00.3
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 4 ports detected
xhci_hcd 0000:0c:00.3: xHCI Host Controller
xhci_hcd 0000:0c:00.3: new USB bus registered, assigned bus number 8
xhci_hcd 0000:0c:00.3: Host supports USB 3.1 Enhanced SuperSpeed
usb usb8: We don't know the algorithms for LPM for this host, disabling LPM.
usb usb8: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.06
usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb8: Product: xHCI Host Controller
usb usb8: Manufacturer: Linux 5.6.11-050611-generic xhci-hcd
usb usb8: SerialNumber: 0000:0c:00.3
hub 8-0:1.0: USB hub found
hub 8-0:1.0: 4 ports detected
i8042: PNP: No PS/2 controller found.
mousedev: PS/2 mouse device common for all mice
rtc_cmos 00:02: RTC can wake from S4
rtc_cmos 00:02: registered as rtc0
rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
i2c /dev entries driver
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.42.0-ioctl (2020-02-27) initialised: dm-devel@redhat.com
platform eisa.0: Probing EISA bus 0
platform eisa.0: EISA: Cannot allocate resource for mainboard
platform eisa.0: Cannot allocate resource for EISA slot 1
platform eisa.0: Cannot allocate resource for EISA slot 2
platform eisa.0: Cannot allocate resource for EISA slot 3
platform eisa.0: Cannot allocate resource for EISA slot 4
platform eisa.0: Cannot allocate resource for EISA slot 5
platform eisa.0: Cannot allocate resource for EISA slot 6
platform eisa.0: Cannot allocate resource for EISA slot 7
platform eisa.0: Cannot allocate resource for EISA slot 8
platform eisa.0: EISA: Detected 0 cards
ledtrig-cpu: registered to indicate activity on CPUs
EFI Variables Facility v0.08 2004-May-17
drop_monitor: Initializing network drop monitor service
NET: Registered protocol family 10
Segment Routing with IPv6
NET: Registered protocol family 17
Key type dns_resolver registered
RAS: Correctable Errors collector initialized.
microcode: CPU0: patch_level=0x08701013
microcode: CPU1: patch_level=0x08701013
microcode: CPU2: patch_level=0x08701013
microcode: CPU3: patch_level=0x08701013
microcode: CPU4: patch_level=0x08701013
microcode: CPU5: patch_level=0x08701013
microcode: CPU6: patch_level=0x08701013
microcode: CPU7: patch_level=0x08701013
microcode: CPU8: patch_level=0x08701013
microcode: CPU9: patch_level=0x08701013
microcode: CPU10: patch_level=0x08701013
microcode: CPU11: patch_level=0x08701013
microcode: CPU12: patch_level=0x08701013
microcode: CPU13: patch_level=0x08701013
microcode: CPU14: patch_level=0x08701013
microcode: CPU15: patch_level=0x08701013
microcode: CPU16: patch_level=0x08701013
microcode: CPU17: patch_level=0x08701013
microcode: CPU18: patch_level=0x08701013
microcode: CPU19: patch_level=0x08701013
microcode: CPU20: patch_level=0x08701013
microcode: CPU21: patch_level=0x08701013
microcode: CPU22: patch_level=0x08701013
microcode: CPU23: patch_level=0x08701013
microcode: CPU24: patch_level=0x08701013
microcode: CPU25: patch_level=0x08701013
microcode: CPU26: patch_level=0x08701013
microcode: CPU27: patch_level=0x08701013
microcode: CPU28: patch_level=0x08701013
microcode: CPU29: patch_level=0x08701013
microcode: CPU30: patch_level=0x08701013
microcode: CPU31: patch_level=0x08701013
microcode: Microcode Update Driver: v2.2.
*** VALIDATE resctrl ***
resctrl: L3 allocation detected
resctrl: L3DATA allocation detected
resctrl: L3CODE allocation detected
resctrl: MB allocation detected
resctrl: L3 monitoring detected
IPI shorthand broadcast: enabled
sched_clock: Marking stable (534451514, 312277333)->(942564691, -95835844)
registered taskstats version 1
Loading compiled-in X.509 certificates
Loaded X.509 cert 'Build time autogenerated kernel key: 2a67b8dd0ca9737fe2253ab71b49a3244a668e30'
zswap: loaded using pool lzo/zbud
Key type ._fscrypt registered
Key type .fscrypt registered
Key type fscrypt-provisioning registered
Key type big_key registered
Key type encrypted registered
AppArmor: AppArmor sha1 policy hashing enabled
integrity: Loading X.509 certificate: UEFI:db
integrity: Loaded X.509 cert 'ASUSTeK MotherBoard SW Key Certificate: da83b990422ebc8c441f8d8b039a65a2'
integrity: Loading X.509 certificate: UEFI:db
integrity: Loaded X.509 cert 'ASUSTeK Notebook SW Key Certificate: b8e581e4df77a5bb4282d5ccfc00c071'
integrity: Loading X.509 certificate: UEFI:db
integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
integrity: Loading X.509 certificate: UEFI:db
integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
integrity: Loading X.509 certificate: UEFI:db
integrity: Loaded X.509 cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63'
ima: No TPM chip found, activating TPM-bypass!
ima: Allocated hash algorithm: sha1
ima: No architecture policies found
evm: Initialising EVM extended attributes:
evm: security.selinux
evm: security.SMACK64
evm: security.SMACK64EXEC
evm: security.SMACK64TRANSMUTE
evm: security.SMACK64MMAP
evm: security.apparmor
evm: security.ima
evm: security.capability
evm: HMAC attrs: 0x1
PM: Magic number: 8:265:436
thermal cooling_device28: hash matches
rtc_cmos 00:02: setting system clock to 2020-06-04T15:24:08 UTC (1591284248)
acpi_cpufreq: overriding BIOS provided _PSD data
Freeing unused decrypted memory: 2040K
Freeing unused kernel image (initmem) memory: 2576K
Write protecting the kernel read-only data: 22528k
Freeing unused kernel image (text/rodata gap) memory: 2044K
Freeing unused kernel image (rodata/data gap) memory: 936K
x86/mm: Checked W+X mappings: passed, no W+X pages found.
Run /init as init process
with arguments:
/init
splash
with environment:
HOME=/
TERM=linux
BOOT_IMAGE=/boot/vmlinuz-5.6.11-050611-generic
acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
dca service started, version 1.12.1
ahci 0000:08:00.0: version 3.0
nvme nvme0: pci function 0000:03:00.0
ahci 0000:08:00.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
ahci 0000:08:00.0: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part
scsi host0: ahci
ata1: SATA max UDMA/133 abar m2048@0xf7500000 port 0xf7500100 irq 66
ahci 0000:09:00.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
ahci 0000:09:00.0: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part
igb: Intel(R) Gigabit Ethernet Network Driver - version 5.6.0-k
igb: Copyright (c) 2007-2014 Intel Corporation.
scsi host1: ahci
ata2: SATA max UDMA/133 abar m2048@0xf7400000 port 0xf7400100 irq 68
ahci 0000:0d:00.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
ahci 0000:0d:00.0: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part
scsi host2: ahci
ata3: SATA max UDMA/133 abar m2048@0xf7e00000 port 0xf7e00100 irq 70
ahci 0000:0e:00.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
ahci 0000:0e:00.0: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part
scsi host3: ahci
ata4: SATA max UDMA/133 abar m2048@0xf7d00000 port 0xf7d00100 irq 77
piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
piix4_smbus 0000:00:14.0: Using register 0x02 for SMBus port selection
cryptd: max_cpu_qlen set to 1000
AVX2 version of gcm_enc/dec engaged.
AES CTR mode by8 optimization enabled
libphy: r8169: probed
r8169 0000:04:00.0 eth0: RTL8125, 04:d9:f5:34:b1:6d, XID 609, IRQ 78
r8169 0000:04:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
r8169 0000:04:00.0 enp4s0: renamed from eth0
MXM: GUID detected in BIOS
checking generic (f1000000 300000) vs hw (e0000000 10000000)
checking generic (f1000000 300000) vs hw (f0000000 2000000)
fb0: switching to nouveaufb from EFI VGA
Console: switching to colour dummy device 80x25
nouveau 0000:0a:00.0: NVIDIA TU104 (164000a1)
pps pps0: new PPS source ptp0
igb 0000:05:00.0: added PHC on eth0
igb 0000:05:00.0: Intel(R) Gigabit Ethernet Network Connection
igb 0000:05:00.0: eth0: (PCIe:2.5Gb/s:Width x1) 04:d9:f5:34:b1:6c
igb 0000:05:00.0: eth0: PBA No: FFFFFF-0FF
igb 0000:05:00.0: Using MSI-X interrupts. 2 rx queue(s), 2 tx queue(s)
igb 0000:05:00.0 enp5s0: renamed from eth0
nouveau 0000:0a:00.0: bios: version 90.04.79.00.01
nouveau 0000:0a:00.0: fb: 8192 MiB GDDR6
[TTM] Zone kernel: Available graphics memory: 8183620 KiB
[TTM] Zone dma32: Available graphics memory: 2097152 KiB
[TTM] Initializing pool allocator
[TTM] Initializing DMA pool allocator
nouveau 0000:0a:00.0: DRM: VRAM: 8192 MiB
nouveau 0000:0a:00.0: DRM: GART: 536870912 MiB
nouveau 0000:0a:00.0: DRM: BIT table 'A' not found
nouveau 0000:0a:00.0: DRM: BIT table 'L' not found
nouveau 0000:0a:00.0: DRM: TMDS table version 2.0
nouveau 0000:0a:00.0: DRM: DCB version 4.1
nouveau 0000:0a:00.0: DRM: DCB outp 00: 02800f66 04600020
nouveau 0000:0a:00.0: DRM: DCB outp 01: 02000f62 00020020
nouveau 0000:0a:00.0: DRM: DCB outp 03: 02011f52 00020010
nouveau 0000:0a:00.0: DRM: DCB outp 04: 04822f76 04600010
nouveau 0000:0a:00.0: DRM: DCB outp 05: 04022f72 00020010
nouveau 0000:0a:00.0: DRM: DCB outp 08: 01844f36 04600010
nouveau 0000:0a:00.0: DRM: DCB outp 09: 01044f32 00020010
nouveau 0000:0a:00.0: DRM: DCB outp 10: 04833f86 04600020
nouveau 0000:0a:00.0: DRM: DCB conn 00: 00020046
nouveau 0000:0a:00.0: DRM: DCB conn 01: 00010161
nouveau 0000:0a:00.0: DRM: DCB conn 02: 01000246
nouveau 0000:0a:00.0: DRM: DCB conn 03: 02000371
nouveau 0000:0a:00.0: DRM: DCB conn 04: 00001446
nouveau 0000:0a:00.0: DRM: MM: using COPY for buffer copies
usb 1-5: new high-speed USB device number 2 using xhci_hcd
usb 3-2: new high-speed USB device number 2 using xhci_hcd
nvme nvme0: missing or invalid SUBNQN field.
nvme nvme0: Shutdown timeout set to 10 seconds
nvme nvme0: 8/0/0 default/read/poll queues
nvme0n1: p1 p2
ata1: SATA link down (SStatus 0 SControl 300)
ata3: SATA link down (SStatus 0 SControl 300)
ata2: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
usb 1-5: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=32.98
usb 1-5: New USB device strings: Mfr=0, Product=1, SerialNumber=0
usb 1-5: Product: USB2.0 Hub
usb 3-2: New USB device found, idVendor=174c, idProduct=2074, bcdDevice= 0.01
usb 3-2: New USB device strings: Mfr=2, Product=3, SerialNumber=0
usb 3-2: Product: ASM107x
usb 3-2: Manufacturer: ASUS TEK.
hub 1-5:1.0: USB hub found
hub 1-5:1.0: 4 ports detected
hub 3-2:1.0: USB hub found
hub 3-2:1.0: 4 ports detected
usb 4-2: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] Driver supports precise vblank timestamp query.
usb 1-6: new full-speed USB device number 3 using xhci_hcd
usb 4-2: New USB device found, idVendor=174c, idProduct=3074, bcdDevice= 0.01
usb 4-2: New USB device strings: Mfr=2, Product=3, SerialNumber=0
usb 4-2: Product: ASM107x
usb 4-2: Manufacturer: ASUS TEK.
hub 4-2:1.0: USB hub found
hub 4-2:1.0: 4 ports detected
usb 1-6: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usb 1-5.3: new full-speed USB device number 4 using xhci_hcd
usb 3-2.2: new high-speed USB device number 3 using xhci_hcd
tsc: Refined TSC clocksource calibration: 3493.434 MHz
clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x325b15e89c7, max_idle_ns: 440795202126 ns
clocksource: Switched to clocksource tsc
usb 1-5.3: config 1 has an invalid interface number: 2 but max is 1
usb 1-5.3: config 1 has no interface number 1
usb 1-5.3: New USB device found, idVendor=0b05, idProduct=18f3, bcdDevice= 1.00
usb 1-5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-5.3: Product: AURA LED Controller
usb 1-5.3: Manufacturer: AsusTek Computer Inc.
usb 1-5.3: SerialNumber: 9876543210
usb 3-2.2: New USB device found, idVendor=0451, idProduct=8142, bcdDevice= 1.00
usb 3-2.2: New USB device strings: Mfr=0, Product=0, SerialNumber=1
usb 3-2.2: SerialNumber: BD040861B5A0
hid: raw HID events driver (C) Jiri Kosina
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
hid-generic 0003:0B05:18F3.0001: hiddev0,hidraw0: USB HID v1.11 Device [AsusTek Computer Inc. AURA LED Controller] on usb-0000:07:00.1-5.3/input2
hub 3-2.2:1.0: USB hub found
hub 3-2.2:1.0: 4 ports detected
usb 4-2.2: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
nouveau 0000:0a:00.0: DRM: allocated 3840x2160 fb: 0x200000, bo 000000009f85a16b
fbcon: nouveaudrmfb (fb0) is primary device
usb 4-2.2: New USB device found, idVendor=0451, idProduct=8140, bcdDevice= 1.00
usb 4-2.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 4-2.2:1.0: USB hub found
hub 4-2.2:1.0: 4 ports detected
usb 3-2.2.1: new low-speed USB device number 4 using xhci_hcd
usb 3-2.2.1: New USB device found, idVendor=04f2, idProduct=0833, bcdDevice= 2.30
usb 3-2.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-2.2.1: Product: USB Keyboard
usb 3-2.2.1: Manufacturer: CHICONY
Console: switching to colour frame buffer device 240x67
input: CHICONY USB Keyboard as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:07:00.3/usb3/3-2/3-2.2/3-2.2.1/3-2.2.1:1.0/0003:04F2:0833.0002/input/input2
hid-generic 0003:04F2:0833.0002: input,hidraw1: USB HID v1.11 Keyboard [CHICONY USB Keyboard] on usb-0000:07:00.3-2.2.1/input0
input: CHICONY USB Keyboard System Control as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:07:00.3/usb3/3-2/3-2.2/3-2.2.1/3-2.2.1:1.1/0003:04F2:0833.0003/input/input3
input: CHICONY USB Keyboard Consumer Control as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:07:00.3/usb3/3-2/3-2.2/3-2.2.1/3-2.2.1:1.1/0003:04F2:0833.0003/input/input4
input: CHICONY USB Keyboard as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:07:00.3/usb3/3-2/3-2.2/3-2.2.1/3-2.2.1:1.1/0003:04F2:0833.0003/input/input5
hid-generic 0003:04F2:0833.0003: input,hiddev1,hidraw2: USB HID v1.11 Device [CHICONY USB Keyboard] on usb-0000:07:00.3-2.2.1/input1
usb 3-2.2.2: new full-speed USB device number 5 using xhci_hcd
nouveau 0000:0a:00.0: fb0: nouveaudrmfb frame buffer device
[drm] Initialized nouveau 1.3.1 20120801 for 0000:0a:00.0 on minor 0
usb 3-2.2.2: New USB device found, idVendor=046d, idProduct=c084, bcdDevice= 7.03
usb 3-2.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 3-2.2.2: Product: G203 Prodigy Gaming Mouse
usb 3-2.2.2: Manufacturer: Logitech
usb 3-2.2.2: SerialNumber: 087E37793234
input: Logitech G203 Prodigy Gaming Mouse as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:07:00.3/usb3/3-2/3-2.2/3-2.2.2/3-2.2.2:1.0/0003:046D:C084.0004/input/input6
hid-generic 0003:046D:C084.0004: input,hidraw3: USB HID v1.11 Mouse [Logitech G203 Prodigy Gaming Mouse] on usb-0000:07:00.3-2.2.2/input0
input: Logitech G203 Prodigy Gaming Mouse Keyboard as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:07:00.3/usb3/3-2/3-2.2/3-2.2.2/3-2.2.2:1.1/0003:046D:C084.0005/input/input7
input: Logitech G203 Prodigy Gaming Mouse Consumer Control as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:07:00.3/usb3/3-2/3-2.2/3-2.2.2/3-2.2.2:1.1/0003:046D:C084.0005/input/input8
input: Logitech G203 Prodigy Gaming Mouse System Control as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:07:00.3/usb3/3-2/3-2.2/3-2.2.2/3-2.2.2:1.1/0003:046D:C084.0005/input/input9
hid-generic 0003:046D:C084.0005: input,hiddev2,hidraw4: USB HID v1.11 Keyboard [Logitech G203 Prodigy Gaming Mouse] on usb-0000:07:00.3-2.2.2/input1
EXT4-fs (nvme0n1p2): mounted filesystem with ordered data mode. Opts: (null)
systemd[1]: Inserted module 'autofs4'
systemd[1]: systemd 245.4-4ubuntu3 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
systemd[1]: Detected architecture x86-64.
systemd[1]: Set hostname to .
systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly.
systemd[1]: Created slice system-modprobe.slice.
systemd[1]: Created slice system-systemd\x2dfsck.slice.
systemd[1]: Created slice User and Session Slice.
systemd[1]: Started Forward Password Requests to Wall Directory Watch.
systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
systemd[1]: Reached target User and Group Name Lookups.
systemd[1]: Reached target Remote File Systems.
systemd[1]: Reached target Slices.
systemd[1]: Listening on Syslog Socket.
systemd[1]: Listening on fsck to fsckd communication Socket.
systemd[1]: Listening on initctl Compatibility Named Pipe.
systemd[1]: Listening on Journal Audit Socket.
systemd[1]: Listening on Journal Socket (/dev/log).
systemd[1]: Listening on Journal Socket.
systemd[1]: Listening on udev Control Socket.
systemd[1]: Listening on udev Kernel Socket.
systemd[1]: Mounting Huge Pages File System...
systemd[1]: Mounting POSIX Message Queue File System...
systemd[1]: Mounting Kernel Debug File System...
systemd[1]: Mounting Kernel Trace File System...
systemd[1]: Starting Journal Service...
systemd[1]: Starting Set the console keyboard layout...
systemd[1]: Starting Create list of static device nodes for the current kernel...
systemd[1]: Condition check resulted in Load Kernel Module drm being skipped.
systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
systemd[1]: Starting Load Kernel Modules...
systemd[1]: Starting Remount Root and Kernel File Systems...
systemd[1]: Starting udev Coldplug all Devices...
systemd[1]: Starting Uncomplicated firewall...
systemd[1]: Mounted Huge Pages File System.
systemd[1]: Mounted POSIX Message Queue File System.
systemd[1]: Mounted Kernel Debug File System.
systemd[1]: Mounted Kernel Trace File System.
systemd[1]: Finished Create list of static device nodes for the current kernel.
EXT4-fs (nvme0n1p2): re-mounted. Opts: errors=remount-ro
systemd[1]: Finished Remount Root and Kernel File Systems.
systemd[1]: Finished Uncomplicated firewall.
systemd[1]: Activating swap /swapfile...
systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
systemd[1]: Starting Load/Save Random Seed...
systemd[1]: Starting Create System Users...
systemd[1]: Finished Set the console keyboard layout.
systemd[1]: Finished Load/Save Random Seed.
lp: driver loaded but no devices found
systemd[1]: Finished Create System Users.
systemd[1]: Starting Create Static Device Nodes in /dev...
ppdev: user-space parallel port driver
systemd[1]: Finished Load Kernel Modules.
systemd[1]: Mounting FUSE Control File System...
systemd[1]: Mounting Kernel Configuration File System...
systemd[1]: Starting Apply Kernel Variables...
systemd[1]: Mounted FUSE Control File System.
systemd[1]: Mounted Kernel Configuration File System.
systemd[1]: Finished Create Static Device Nodes in /dev.
systemd[1]: Reached target Local File Systems (Pre).
systemd[1]: Mounting Mount unit for core18, revision 1705...
systemd[1]: Mounting Mount unit for core18, revision 1754...
systemd[1]: Mounting Mount unit for gnome-3-34-1804, revision 27...
systemd[1]: Mounting Mount unit for gnome-3-34-1804, revision 33...
systemd[1]: Mounting Mount unit for gtk-common-themes, revision 1506...
systemd[1]: Mounting Mount unit for snap-store, revision 433...
systemd[1]: Mounting Mount unit for snap-store, revision 454...
systemd[1]: Mounting Mount unit for snapd, revision 7264...
systemd[1]: Starting udev Kernel Device Manager...
systemd[1]: Finished Apply Kernel Variables.
systemd[1]: Finished udev Coldplug all Devices.
systemd[1]: Starting Helper to synchronize boot up for ifupdown...
systemd[1]: Finished Helper to synchronize boot up for ifupdown.
Adding 2097148k swap on /swapfile. Priority:-2 extents:6 across:2260988k SSFS
systemd[1]: Activated swap /swapfile.
systemd[1]: Reached target Swap.
systemd[1]: Mounted Mount unit for core18, revision 1754.
systemd[1]: Started Journal Service.
systemd-journald[645]: Received client request to flush runtime journal.
asus_wmi: ASUS WMI generic driver loaded
asus_wmi: Initialization: 0x0
asus_wmi: BIOS WMI version: 0.9
asus_wmi: SFUN value: 0x0
eeepc-wmi eeepc-wmi: Detected ASUSWMI, use DCTS
input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input12
ccp 0000:0c:00.1: enabling device (0000 -> 0002)
ccp 0000:0c:00.1: ccp: unable to access the device: you might be running a broken BIOS.
kvm: disabled by bios
kvm: disabled by bios
IPMI message handler: version 39.2
ipmi device interface
MCE: In-kernel MCE decoding enabled.
snd_hda_intel 0000:0a:00.1: Disabling MSI
snd_hda_intel 0000:0a:00.1: Handle vga_switcheroo audio client
snd_hda_intel 0000:0c:00.4: enabling device (0000 -> 0002)
kvm: disabled by bios
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
cfg80211: Loading compiled-in X.509 certificates for regulatory database
cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
snd_hda_intel 0000:0a:00.1: bound 0000:0a:00.0 (ops nv50_audio_component_bind_ops [nouveau])
input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.1/0000:0a:00.1/sound/card0/input13
input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.1/0000:0a:00.1/sound/card0/input14
input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.1/0000:0a:00.1/sound/card0/input15
input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.1/0000:0a:00.1/sound/card0/input16
input: HDA NVidia HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:03.1/0000:0a:00.1/sound/card0/input17
input: HDA NVidia HDMI/DP,pcm=11 as /devices/pci0000:00/0000:00:03.1/0000:0a:00.1/sound/card0/input18
input: HDA NVidia HDMI/DP,pcm=12 as /devices/pci0000:00/0000:00:03.1/0000:0a:00.1/sound/card0/input19
snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC1220: line_outs=3 (0x14/0x15/0x16/0x0/0x0) type:line
snd_hda_codec_realtek hdaudioC1D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
snd_hda_codec_realtek hdaudioC1D0: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
snd_hda_codec_realtek hdaudioC1D0: mono: mono_out=0x0
snd_hda_codec_realtek hdaudioC1D0: dig-out=0x1e/0x0
snd_hda_codec_realtek hdaudioC1D0: inputs:
snd_hda_codec_realtek hdaudioC1D0: Front Mic=0x19
snd_hda_codec_realtek hdaudioC1D0: Rear Mic=0x18
snd_hda_codec_realtek hdaudioC1D0: Line=0x1a
input: HD-Audio Generic Front Mic as /devices/pci0000:00/0000:00:08.1/0000:0c:00.4/sound/card1/input20
input: HD-Audio Generic Rear Mic as /devices/pci0000:00/0000:00:08.1/0000:0c:00.4/sound/card1/input21
input: HD-Audio Generic Line as /devices/pci0000:00/0000:00:08.1/0000:0c:00.4/sound/card1/input22
input: HD-Audio Generic Line Out Front as /devices/pci0000:00/0000:00:08.1/0000:0c:00.4/sound/card1/input23
input: HD-Audio Generic Line Out Surround as /devices/pci0000:00/0000:00:08.1/0000:0c:00.4/sound/card1/input24
input: HD-Audio Generic Line Out CLFE as /devices/pci0000:00/0000:00:08.1/0000:0c:00.4/sound/card1/input25
input: HD-Audio Generic Front Headphone as /devices/pci0000:00/0000:00:08.1/0000:0c:00.4/sound/card1/input26
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
kvm: disabled by bios
Bluetooth: Core ver 2.22
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
Intel(R) Wireless WiFi driver for Linux
Copyright(c) 2003- 2015 Intel Corporation
iwlwifi 0000:06:00.0: enabling device (0000 -> 0002)
iwlwifi 0000:06:00.0: Direct firmware load for iwlwifi-cc-a0-52.ucode failed with error -2
iwlwifi 0000:06:00.0: Direct firmware load for iwlwifi-cc-a0-51.ucode failed with error -2
iwlwifi 0000:06:00.0: Direct firmware load for iwlwifi-cc-a0-50.ucode failed with error -2
iwlwifi 0000:06:00.0: Direct firmware load for iwlwifi-cc-a0-49.ucode failed with error -2
EDAC amd64: F17h_M70h detected (node 0).
kvm: disabled by bios
EDAC amd64: Node 0: DRAM ECC disabled.
iwlwifi 0000:06:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17
iwlwifi 0000:06:00.0: Found debug destination: EXTERNAL_DRAM
iwlwifi 0000:06:00.0: Found debug configuration: 0
iwlwifi 0000:06:00.0: loaded firmware version 48.4fa0041f.0 cc-a0-48.ucode op_mode iwlmvm
EDAC amd64: F17h_M70h detected (node 0).
kvm: disabled by bios
EDAC amd64: Node 0: DRAM ECC disabled.
usbcore: registered new interface driver btusb
Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
Bluetooth: hci0: Device revision is 1
Bluetooth: hci0: Secure boot is enabled
Bluetooth: hci0: OTP lock is enabled
Bluetooth: hci0: API lock is enabled
Bluetooth: hci0: Debug lock is disabled
Bluetooth: hci0: Minimum firmware build 1 week 10 2014
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
kvm: disabled by bios
Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
nvidia: loading out-of-tree module taints kernel.
nvidia: module license 'NVIDIA' taints kernel.
Disabling lock debugging due to kernel taint
nvidia: module verification failed: signature and/or required key missing - tainting kernel
EDAC amd64: F17h_M70h detected (node 0).
kvm: disabled by bios
EDAC amd64: Node 0: DRAM ECC disabled.
iwlwifi 0000:06:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
iwlwifi 0000:06:00.0: Applying debug destination EXTERNAL_DRAM
iwlwifi 0000:06:00.0: Allocated 0x00400000 bytes for firmware monitor.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
kvm: disabled by bios
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
iwlwifi 0000:06:00.0: base HW address: 38:00:25:4d:74:98
thermal thermal_zone0: failed to read out thermal zone (-61)
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
iwlwifi 0000:06:00.0 wlp6s0: renamed from wlan0
kvm: disabled by bios
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
audit: type=1400 audit(1591284253.908:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/haveged" pid=1005 comm="apparmor_parser"
audit: type=1400 audit(1591284253.908:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" pid=988 comm="apparmor_parser"
audit: type=1400 audit(1591284253.908:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-senddoc" pid=996 comm="apparmor_parser"
audit: type=1400 audit(1591284253.908:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="ippusbxd" pid=994 comm="apparmor_parser"
audit: type=1400 audit(1591284253.908:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-oopslash" pid=989 comm="apparmor_parser"
audit: type=1400 audit(1591284253.912:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=993 comm="apparmor_parser"
audit: type=1400 audit(1591284253.912:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=993 comm="apparmor_parser"
audit: type=1400 audit(1591284253.912:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=991 comm="apparmor_parser"
audit: type=1400 audit(1591284253.912:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=1004 comm="apparmor_parser"
audit: type=1400 audit(1591284253.912:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=995 comm="apparmor_parser"
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
Bluetooth: hci0: Waiting for firmware download to complete
Bluetooth: hci0: Firmware loaded in 1284231 usecs
Bluetooth: hci0: Waiting for device to boot
Bluetooth: hci0: Device booted in 14640 usecs
Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
Bluetooth: hci0: Failed to send Intel_Write_DDC (-22)
Bluetooth: hci0: Firmware revision 0.0 build 128 week 11 2020
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
EDAC amd64: F17h_M70h detected (node 0).
EDAC amd64: Node 0: DRAM ECC disabled.
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: BNEP socket layer initialized
NET: Registered protocol family 38
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
RTL8125 2.5Gbps internal r8169-400:00: attached PHY driver [RTL8125 2.5Gbps internal] (mii_bus:phy_addr=r8169-400:00, irq=IGNORE)
r8169 0000:04:00.0 enp4s0: Link is Down
iwlwifi 0000:06:00.0: Applying debug destination EXTERNAL_DRAM
iwlwifi 0000:06:00.0: FW already configured (0) - re-configuring
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
r8169 0000:04:00.0 enp4s0: Link is Up - 1Gbps/Full - flow control rx/tx
IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
rfkill: input handler disabled
kauditd_printk_skb: 28 callbacks suppressed
audit: type=1400 audit(1591284275.928:40): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/snap/snapd/7777/usr/lib/snapd/snap-confine" pid=2218 comm="apparmor_parser"
audit: type=1400 audit(1591284275.928:41): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/snap/snapd/7777/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=2218 comm="apparmor_parser"
audit: type=1400 audit(1591284276.252:42): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap-update-ns.snap-store" pid=2220 comm="apparmor_parser"
audit: type=1400 audit(1591284276.256:43): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.snap-store.ubuntu-software" pid=2223 comm="apparmor_parser"
audit: type=1400 audit(1591284276.256:44): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.snap-store.snap-store" pid=2222 comm="apparmor_parser"
audit: type=1400 audit(1591284276.256:45): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.snap-store.ubuntu-software-local-file" pid=2224 comm="apparmor_parser"
rfkill: input handler enabled
audit: type=1400 audit(1591284278.040:46): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/snap/snapd/7777/usr/lib/snapd/snap-confine" pid=2380 comm="apparmor_parser"
audit: type=1400 audit(1591284278.080:47): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/snap/snapd/7777/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=2380 comm="apparmor_parser"
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
audit: type=1400 audit(1591284278.304:48): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.snap-store" pid=2393 comm="apparmor_parser"
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
audit: type=1400 audit(1591284278.308:49): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.snap-store.ubuntu-software-local-file" pid=2451 comm="apparmor_parser"
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
rfkill: input handler disabled
rfkill: input handler enabled
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
rfkill: input handler disabled
rfkill: input handler enabled
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA devices probed.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511